A Microsoft Office up grade can be intimidating, particularly for companies still using office 2013 enterprise . The distance between Office 2003 and Office 2010 can incite fears of compatibility problems and business disruptions in the minds of IT managers.

But with Windows 7 updates and hardware refreshes picking up speed this calendar year, so too will Office upgrades, according to a December, 2010 Forrester research report entitled "Pitfalls To Avoid When Upgrading To office 2013 home and student " by researcher Philipp Karcher with Stephen Powers, Christopher Voce, and Joseph Dang.

The recipe for a successful enterprise Office improve includes "a heavy dose of planning, an ample amount of input from the business, a package of training, and just the right amount of remediation to minimize risk," the report states.Most with the companies that only recently upgraded to Office 2007 will wait on upgrades, Forrester predicts. But for the many businesses that did not improve to Office 2007 or Windows Vista, 2011 is going to be the 12 months to take on both Office and Windows upgrades, and thereby minimize employee disruption.

Forrester forecasts that IT spending on desktop applications, including Office, will experience steady growth of 7 percent in 2011. Similarly, Gartner expects enterprise software spending to grow 7.5 percent year-over-year in 2011, up from 6.1 percent in 2010.Yet despite the loosening of IT budgets, IT departments still face a lengthy process with microsoft office 2013 professional upgrades that requires environmental assessments, file migrations, application testing, and training of workers, often with different considerations for different business units. And with these update challenges, come pitfalls.

Here are four Office 2010 upgrade pitfalls to avoid, according to Forrester.The most common cause of business disruption with Office updates is file and application incompatibility, writes Forrester. This will require the most work and planning. The top compatibility issues include unsupported VBA (Visual Basic for Applications) syntax, hidden commands, broken file links, invalid range names and 64-bit compatibility.

Again, the severity of these issues is intensified when going from Office 2003 to visio professional 2013 . Forrester recommends that IT teams focus on compatibility issues that affect the company's Office files and templates, as well as add-ins that extend the functionality of Office, and also the integration with non-Office applications this sort of as content management and CRM apps.The Forrester report recommends using tools out there from Microsoft and third parties to assess compatibility issues and fix incompatible code, however third-party add-ins will require that you follow up with all the vendor, Forrester warns.

4